Cryptext x64 0.11x fix2 targeted tests
======================================

Build with the user's reference FASM 1.73.35. No successful build is claimed by
the source-generation environment.

A. Large folder regression
1. Use a readable folder tree containing >2,000 files.
2. Right-click the folder -> Encrypt.
3. Verify the old 65,536-WCHAR "recursive file list is too large" condition is
   no longer reached merely because of this file count.
4. Verify progress/batch processing begins and every file remains an independent
   normal Cryptext transaction.
5. Repeat with folder -> Decrypt after producing .$#! files.

B. Per-file access denied
1. Use a folder that can be enumerated but contains a file Cryptext cannot open,
   e.g. a protected file under Program Files when applicable.
2. Verify the existing detailed per-file error appears with the concrete path.
3. Verify "continue with next file?" still works.

C. Directory-enumeration access denied
1. Use a directory/subdirectory whose contents themselves cannot be enumerated.
2. Verify folder expansion aborts before any file is changed and the folder-level
   access-denied diagnostic is shown.

D. Small folder / normal file regression
- small recursive Encrypt
- small recursive Decrypt
- file-only Explorer Encrypt/Decrypt
- file Drag & Drop
- normal common-dialog multi-select
All should behave as in 0.11x fix1.

E. Reparse points
Verify junctions/symlinks are still not followed.

F. Crypto regression
Re-test at least one CT64FILE v1 file and one known Cryptext 3.4 legacy file.
Neither crypto path was intentionally changed.
